[DirectX] I cant figure out this error...

**Raigne** · 09-05-2008

I tried using the DXTrace function, but all it says even if i make an error occur is unknown error. It doesn't show the file or line number like the docs say it should.
I am linking against DxErr9.lib ( i tried dxErr.lib also ).
This is how i am using it. Am I doing this wrong?

Code:

HRESULT RetVal = sData->d3D->CreateDevice(D3DADAPTER_DEFAULT,
                      D3DDEVTYPE_HAL,
                      sData->hWnd,
                      D3DCREATE_HARDWARE_VERTEXPROCESSING,
                      &d3dpp,
                      &sData->d3DDev);
	if ( RetVal != D3D_OK )
	{
		DXTrace(__FILE__,__LINE__,RetVal,NULL,TRUE);
		Shutdown();
		exit(1);
	}

**abachler** · 09-05-2008

Are you using getdevcaps to make sure your device can handle the settings you are putting into d3dpp? Try printing otu teh actual hexadecimal code that is returned in RetVal.

**Raigne** · 09-05-2008

That code will not work on this computer. I purposely made it so. I am trying to figure out why

Code:

DXTrace(__FILE__,__LINE__,RetVal,NULL,TRUE);

is not working.

I have attached a image of the screen when the message box is showing. It has absolutely no information in it.

I can do

Code:

DXTrace(__FILE__,__LINE__,RetVal,NULL,FALSE);

and the debug message shows the information in the debugger window, but I want to have message box errors.

Bubba:

the doc states that you can set D3DFMT_UNKNOWN in windowed mode, but do not have to.

Originally Posted by Documentation

BackBufferFormat
The back buffer format. For more information about formats, see D3DFORMAT. This value must be one of the render-target formats as validated by IDirect3D9::CheckDeviceType. You can use IDirect3DDevice9::GetDisplayMode to obtain the current format.
In fact, D3DFMT_UNKNOWN can be specified for the BackBufferFormat while in windowed mode. This tells the runtime to use the current display-mode format and eliminates the need to call IDirect3DDevice9::GetDisplayMode.

For windowed applications, the back buffer format no longer needs to match the display-mode format because color conversion can now be done by the hardware (if the hardware supports color conversion). The set of possible back buffer formats is constrained, but the runtime will allow any valid back buffer format to be presented to any desktop format. (There is the additional requirement that the device be operable in the desktop mode; devices typically do not operate in 8 bits per pixel modes.)

Full-screen applications cannot do color conversion.

**Elysia** · 09-05-2008

You can use alt+print screen to take a snapshot only of the dialog, you know...
You can also try DXGetErrorString9 or whatever it's called. It gets the error description from an error code.
Then just print it.

**Raigne** · 09-05-2008

I understand that, but kind of odd that the DX function does not work.

Thread: [DirectX] I cant figure out this error...

Thread Tools

Search Thread

Display

Similar Threads

Compiling sample DarkGDK Program

Testing some code, lots of errors...

Post...

ras.h errors

Linking error